Skip to main content

This is a new service – your feedback will help us to improve it.

Buckinghamshire Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

South Bucks Council (No. 12) Tree Preservation Order 1992; dated 10/11/92; made under Sections 198;

reference
ZZZZZTESRW187
name
South Bucks Council (No. 12) Tree Preservation Order 1992; dated 10/11/92; made under Sections 198;
tree-preservation-order

undefined

TPO/SBDC/1992/12
tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.485811 51.573667,-0.485800 51.573711,-0.485791 51.573738,-0.485784 51.573780,-0.485766 51.573863,-0.485758 51.573875,-0.485742 51.573893,-0.485712 51.573913,-0.485666 51.573949,-0.485614 51.573993,-0.485595 51.574004,-0.485583 51.574013,-0.485567 51.574022,-0.485519 51.574041,-0.485425 51.574066,-0.484898 51.574229,-0.484835 51.574250,-0.484788 51.574271,-0.484722 51.574304,-0.484635 51.574370,-0.484468 51.574514,-0.484352 51.574623,-0.484313 51.574662,-0.484219 51.574768,-0.484156 51.574848,-0.484129 51.574908,-0.484113 51.574949,-0.484102 51.574992,-0.484093 51.575037,-0.484143 51.575042,-0.484182 51.574917,-0.484187 51.574894,-0.484194 51.574885,-0.484212 51.574876,-0.484289 51.574859,-0.484467 51.574808,-0.484537 51.574772,-0.485339 51.574341,-0.486075 51.573932,-0.486117 51.573894,-0.486137 51.573869,-0.486144 51.573844,-0.486145 51.573816,-0.486136 51.573784,-0.486126 51.573767,-0.486102 51.573752,-0.486066 51.573731,-0.485935 51.573679,-0.485854 51.573666,-0.485811 51.573667)))
point
POINT (-0.485135 51.5743)
notes
entry-date
2017-07-04
start-date
2017-07-04
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Buckinghamshire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL